Update Publisher (v1.0.0)

Update a publisher

Command PUT Publisher Admin Only

Overview

Update an existing publisher in the catalog domain. This endpoint follows Domain-Driven Design principles, where the publisher entity is part of the catalog bounded context. When a publisher is updated, the command is validated against business rules before being processed by the domain service.

The operation is idempotent and ensures data integrity through optimistic concurrency control. If the publisher doesn’t exist, the system will return an appropriate error response rather than creating a new entity, maintaining the command-query separation principle.

This endpoint supports the catalog domain’s business capability to manage publisher information as a core domain concept.

Architecture

PUT (/api/v1/publishers/{id})

Parameters

  • id (path) (required) - The unique identifier of the publisher to update (GUID format)

Request Body

Example Usage

Terminal window
curl -X PUT "https://api.bookworm.com/api/v1/publishers/{id}" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer <admin-token>" \
  -d '{"name": "Updated Publisher Name"}'

Authorization

This endpoint requires admin-level authorization to access. The request must include a valid authentication token with the appropriate admin privileges.

Validation Rules

The following validation rules are applied to the request:

  1. Publisher ID:

    • Must not be empty
    • Must be a valid GUID format

  2. Publisher Name:

    • Must not be empty
    • Maximum length: Medium (as defined in DataSchemaLength)

Responses

400 Bad Request

Returned when the request validation fails. This includes:

  • Invalid publisher ID format
  • Empty or invalid publisher name
  • Name exceeds maximum length

401 Unauthorized

Returned when the request is not authenticated or the user lacks admin privileges.

404 Not Found

Returned when the specified publisher ID does not exist in the system.

204 No Content

Returned when the publisher is successfully updated. The response body is empty.

Error Handling

The endpoint implements proper error handling for various scenarios:

  • Validation errors are returned as 400 Bad Request
  • Authentication/Authorization errors return 401 Unauthorized
  • Non-existent publishers return 404 Not Found
  • Server errors return appropriate 5xx status codes

Versioning

This endpoint is available in API version 1.0.